home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 1998 November / IRIX 6.5.2 Base Documentation November 1998.img / usr / share / catman / u_man / cat3 / Tk / managegeom.z / managegeom
Text File  |  1998-10-30  |  7KB  |  133 lines
  1.  
  2.  
  3.  
  4. TTTTkkkk____MMMMaaaannnnaaaaggggeeeeGGGGeeeeoooommmmeeeettttrrrryyyy((((3333TTTTkkkk))))                                  TTTTkkkk____MMMMaaaannnnaaaaggggeeeeGGGGeeeeoooommmmeeeettttrrrryyyy((((3333TTTTkkkk))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      Tk_ManageGeometry - arrange to handle geometry requests for a window
  10.  
  11. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      ####iiiinnnncccclllluuuuddddeeee <<<<ttttkkkk....hhhh>>>>
  13.  
  14.      TTTTkkkk____MMMMaaaannnnaaaaggggeeeeGGGGeeeeoooommmmeeeettttrrrryyyy(_t_k_w_i_n, _m_g_r_P_t_r, _c_l_i_e_n_t_D_a_t_a)                             |
  15.  
  16. AAAARRRRGGGGUUUUMMMMEEEENNNNTTTTSSSS
  17.      Tk_Window         _t_k_w_i_n        (in)      Token for window to be managed. |
  18.  
  19.      Tk_GeomMgr        *_m_g_r_P_t_r      (in)      Pointer to data structure       |
  20.                                               containing information about the|
  21.                                               geometry manager, or NULL to    |
  22.                                               indicate that _t_k_w_i_n's geometry  |
  23.                                               shouldn't be managed anymore.   |
  24.                                               The data structure pointed to by|
  25.                                               _m_g_r_P_t_r must be static:  Tk keeps|
  26.                                               a reference to it as long as the|
  27.                                               window is managed.
  28.  
  29.      ClientData        _c_l_i_e_n_t_D_a_t_a   (in)      Arbitrary one-word value to pass|
  30.                                               to geometry manager callbacks.
  31.  
  32.  
  33. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  34.      TTTTkkkk____MMMMaaaannnnaaaaggggeeeeGGGGeeeeoooommmmeeeettttrrrryyyy arranges for a particular geometry manager, described
  35.      by the _m_g_r_P_t_r argument, to control the geometry of a particular slave
  36.      window, given by _t_k_w_i_n.  If _t_k_w_i_n was previously managed by some other
  37.      geometry manager, the previous manager loses control in favor of the new
  38.      one.  If _m_g_r_P_t_r is NULL, geometry management is cancelled for _t_k_w_i_n.
  39.  
  40.      The structure pointed to by _m_g_r_P_t_r contains information about the
  41.      geometry manager:
  42.           ttttyyyyppppeeeeddddeeeeffff ssssttttrrrruuuucccctttt {{{{
  43.                cccchhhhaaaarrrr ****_n_a_m_e;;;;
  44.                TTTTkkkk____GGGGeeeeoooommmmRRRReeeeqqqquuuueeeessssttttPPPPrrrroooocccc ****_r_e_q_u_e_s_t_P_r_o_c;;;;
  45.                TTTTkkkk____GGGGeeeeoooommmmLLLLoooossssttttSSSSllllaaaavvvveeeePPPPrrrroooocccc ****_l_o_s_t_S_l_a_v_e_P_r_o_c;;;;
  46.           }}}} TTTTkkkk____GGGGeeeeoooommmmMMMMggggrrrr;;;;
  47.      The _n_a_m_e field is the textual name for the geometry manager, such as ppppaaaacccckkkk
  48.      or ppppllllaaaacccceeee;  this value will be returned by the command wwwwiiiinnnnffffoooo mmmmaaaannnnaaaaggggeeeerrrr.
  49.  
  50.      _r_e_q_u_e_s_t_P_r_o_c is a procedure in the geometry manager that will be invoked
  51.      whenever TTTTkkkk____GGGGeeeeoooommmmeeeettttrrrryyyyRRRReeeeqqqquuuueeeesssstttt is called by the slave to change its desired
  52.      geometry.  _r_e_q_u_e_s_t_P_r_o_c should have arguments and results that match the
  53.      type TTTTkkkk____GGGGeeeeoooommmmRRRReeeeqqqquuuueeeessssttttPPPPrrrroooocccc:
  54.           ttttyyyyppppeeeeddddeeeeffff vvvvooooiiiidddd TTTTkkkk____GGGGeeeeoooommmmRRRReeeeqqqquuuueeeessssttttPPPPrrrroooocccc((((
  55.                CCCClllliiiieeeennnnttttDDDDaaaattttaaaa _c_l_i_e_n_t_D_a_t_a,,,,
  56.                TTTTkkkk____WWWWiiiinnnnddddoooowwww _t_k_w_i_n))));;;;
  57.      The parameters to _r_e_q_u_e_s_t_P_r_o_c will be identical to the corresponding
  58.      parameters passed to TTTTkkkk____MMMMaaaannnnaaaaggggeeeeGGGGeeeeoooommmmeeeettttrrrryyyy.  _c_l_i_e_n_t_D_a_t_a usually points to a
  59.      data structure containing application-specific information about how to
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. TTTTkkkk____MMMMaaaannnnaaaaggggeeeeGGGGeeeeoooommmmeeeettttrrrryyyy((((3333TTTTkkkk))))                                  TTTTkkkk____MMMMaaaannnnaaaaggggeeeeGGGGeeeeoooommmmeeeettttrrrryyyy((((3333TTTTkkkk))))
  71.  
  72.  
  73.  
  74.      manage _t_k_w_i_n's geometry.
  75.  
  76.      The _l_o_s_t_S_l_a_v_e_P_r_o_c field of _m_g_r_P_t_r points to another procedure in the
  77.      geometry manager.  Tk will invoke _l_o_s_t_S_l_a_v_e_P_r_o_c if some other manager
  78.      calls TTTTkkkk____MMMMaaaannnnaaaaggggeeeeGGGGeeeeoooommmmeeeettttrrrryyyy to claim _t_k_w_i_n away from the current geometry
  79.      manager.  _l_o_s_t_S_l_a_v_e_P_r_o_c is not invoked if TTTTkkkk____MMMMaaaannnnaaaaggggeeeeGGGGeeeeoooommmmeeeettttrrrryyyy is called
  80.      with a NULL value for _m_g_r_P_t_r (presumably the current geometry manager has
  81.      made this call, so it already knows that the window is no longer
  82.      managed), nor is it called if _m_g_r_P_t_r is the same as the window's current
  83.      geometry manager.  _l_o_s_t_S_l_a_v_e_P_r_o_c should have arguments and results that
  84.      match the following prototype:
  85.           ttttyyyyppppeeeeddddeeeeffff vvvvooooiiiidddd TTTTkkkk____GGGGeeeeoooommmmLLLLoooossssttttSSSSllllaaaavvvveeeePPPPrrrroooocccc((((
  86.                CCCClllliiiieeeennnnttttDDDDaaaattttaaaa _c_l_i_e_n_t_D_a_t_a,,,,
  87.                TTTTkkkk____WWWWiiiinnnnddddoooowwww _t_k_w_i_n))));;;;
  88.      The parameters to _l_o_s_t_S_l_a_v_e_P_r_o_c will be identical to the corresponding
  89.      parameters passed to TTTTkkkk____MMMMaaaannnnaaaaggggeeeeGGGGeeeeoooommmmeeeettttrrrryyyy.
  90.  
  91.  
  92. KKKKEEEEYYYYWWWWOOOORRRRDDDDSSSS
  93.      callback, geometry, managed, request, unmanaged
  94.  
  95.  
  96.  
  97.  
  98.  
  99.  
  100.  
  101.  
  102.  
  103.  
  104.  
  105.  
  106.  
  107.  
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.                                                                         PPPPaaaaggggeeee 2222
  130.  
  131.  
  132.  
  133.